SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Internet Protocol</title>

</head>

Internet Protocol

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1246091330">

/* start https://en.wikipedia.org/ */

.mw-parser-output .sidebar{width:22em;float:right;clear:right;margin:0.5em 0 1em 1em;background:var(--background-color-neutral-subtle,#f8f9fa);border:1px solid var(--border-color-base,#a2a9b1);padding:0.2em;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse;display:table}body.skin-minerva .mw-parser-output .sidebar{display:table!important;float:right!important;margin:0.5em 0 1em 1em!important}.mw-parser-output .sidebar-subgroup{width:100%;margin:0;border-spacing:0}.mw-parser-output .sidebar-left{float:left;clear:left;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-none{float:none;clear:both;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-outer-title{padding:0 0.4em 0.2em;font-size:125%;line-height:1.2em;font-weight:bold}.mw-parser-output .sidebar-top-image{padding:0.4em}.mw-parser-output .sidebar-top-caption,.mw-parser-output .sidebar-pretitle-with-top-image,.mw-parser-output .sidebar-caption{padding:0.2em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-pretitle{padding:0.4em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-title,.mw-parser-output .sidebar-title-with-pretitle{padding:0.2em 0.8em;font-size:145%;line-height:1.2em}.mw-parser-output .sidebar-title-with-pretitle{padding:0.1em 0.4em}.mw-parser-output .sidebar-image{padding:0.2em 0.4em 0.4em}.mw-parser-output .sidebar-heading{padding:0.1em 0.4em}.mw-parser-output .sidebar-content{padding:0 0.5em 0.4em}.mw-parser-output .sidebar-content-with-subgroup{padding:0.1em 0.4em 0.2em}.mw-parser-output .sidebar-above,.mw-parser-output .sidebar-below{padding:0.3em 0.8em;font-weight:bold}.mw-parser-output .sidebar-collapse .sidebar-above,.mw-parser-output .sidebar-collapse .sidebar-below{border-top:1px solid #aaa;border-bottom:1px solid #aaa}.mw-parser-output .sidebar-navbar{text-align:right;font-size:115%;padding:0 0.4em 0.4em}.mw-parser-output .sidebar-list-title{padding:0 0.4em;text-align:left;font-weight:bold;line-height:1.6em;font-size:105%}.mw-parser-output .sidebar-list-title-c{padding:0 0.4em;text-align:center;margin:0 3.3em}@media(max-width:640px){body.mediawiki .mw-parser-output .sidebar{width:100%!important;clear:both;float:none!important;margin-left:0!important;margin-right:0!important}}body.skin--responsive .mw-parser-output .sidebar a>img{max-width:none!important}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media print{body.ns-0 .mw-parser-output .sidebar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><table class="sidebar nomobile nowraplinks hlist"><tbody><tr><th class="sidebar-title"><a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a></th></tr><tr><th class="sidebar-heading">

<a href="Application_layer" title="Application layer">Application layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="HTTPS" title="HTTPS">HTTPS</a></li>

<li><a href="Telnet" title="Telnet">Telnet</a></li>

</tr><tr><th class="sidebar-heading">

<a href="Transport_layer" title="Transport layer">Transport layer</a></th></tr><tr><td class="sidebar-content">

</tr><tr><th class="sidebar-heading">

<a href="Internet_layer" title="Internet layer">Internet layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="IPsec" title="IPsec">IPsec</a></li>

</tr><tr><th class="sidebar-heading">

<a href="Link_layer" title="Link layer">Link layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="Tunneling_protocol" title="Tunneling protocol">Tunnels</a></li>

</tr><tr><td class="sidebar-navbar"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></td></tr></tbody></table>

<td style="background: #ccf; text-align: center;">Internet history timeline

</td></tr>

<tr>

<td>

Early research and development:

<ul><li>1960–1962: <a href="J._C._R._Licklider" title="J. C. R. Licklider">J. C. R. Licklider</a> networking ideas</li>

<li>1960–1964: <a href="RAND" class="mw-redirect" title="RAND">RAND</a> networking concepts developed</li>

<li>1962–1964: <a href="DARPA" title="DARPA">ARPA</a> networking ideas</li>

<li>1965 (1965): <a href="NPL_network" title="NPL network">NPL network</a> concepts conceived</li>

<li>1966 (1966): <a href="Merit_Network" title="Merit Network">Merit Network</a> founded</li>

<li>1967 (1967): <a href="ARPANET" title="ARPANET">ARPANET</a> planning begins</li>

<li>1967 (1967): <a href="Symposium_on_Operating_Systems_Principles" title="Symposium on Operating Systems Principles">Symposium on Operating Systems Principles</a></li>

<li>1969 (1969): NPL followed by the ARPANET carry their first packets</li>

<li>1970 (1970): <a href="InterNIC#History" title="InterNIC">Network Information Center</a> (NIC)</li>

<li>1971 (1971): <a href="Tymnet" title="Tymnet">Tymnet</a> switched-circuit network</li>

<li>1972 (1972): Merit Network's packet-switched network operational</li>

<li>1972 (1972): <a href="Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">Internet Assigned Numbers Authority</a> (IANA) established</li>

<li>1973 (1973): <a href="CYCLADES" title="CYCLADES">CYCLADES</a> network demonstrated</li>

<li>1973 (1973): <a href="PARC_Universal_Packet" title="PARC Universal Packet">PARC Universal Packet</a> development begins</li>

<li>1974 (1974): <a href="Transmission_Control_Program" class="mw-redirect" title="Transmission Control Program">Transmission Control Program</a> specification published</li>

<li>1975 (1975): <a href="Telenet" title="Telenet">Telenet</a> commercial packet-switched network</li>

<li>1976 (1976): <a href="X.25" title="X.25">X.25</a> protocol approved and deployed on <a href="Public_data_network" title="Public data network">public data networks</a></li>

<li>1978 (1978): <a href="Minitel" title="Minitel">Minitel</a> introduced</li>

<li>1979 (1979): <a href="Internet_Architecture_Board" title="Internet Architecture Board">Internet Activities Board</a> (IAB)</li>

<li>1980 (1980): <a href="Usenet" title="Usenet">USENET</a> news using <a href="UUCP" title="UUCP">UUCP</a></li>

<li>1980 (1980): <a href="Ethernet" title="Ethernet">Ethernet</a> standard introduced</li>

<li>1981 (1981): <a href="BITNET" title="BITNET">BITNET</a> established</li></ul>

Merging the networks and creating the Internet:

<ul><li>1981 (1981): <a href="CSNET" title="CSNET">Computer Science Network</a> (CSNET)</li>

<li>1982 (1982): <a href="Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a> protocol suite formalized</li>

<li>1982 (1982): <a href="Simple_Mail_Transfer_Protocol" title="Simple Mail Transfer Protocol">Simple Mail Transfer Protocol</a> (SMTP)</li>

<li>1983 (1983): <a href="Domain_Name_System" title="Domain Name System">Domain Name System</a> (DNS)</li>

<li>1983 (1983): <a href="MILNET" title="MILNET">MILNET</a> split off from ARPANET</li>

<li>1984 (1984): <a href="OSI_model" title="OSI model">OSI Reference Model</a> released</li>

<li>1985 (1985): <a href="Domain_names" class="mw-redirect" title="Domain names">First .COM domain name registered</a></li>

<li>1986 (1986): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> with 56 kbit/s links</li>

<li>1986 (1986): <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF)</li>

<li>1987 (1987): <a href="UUNET" title="UUNET">UUNET</a> founded</li>

<li>1988 (1988): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> upgraded to 1.5 Mbit/s (T1)</li>

<li>1988 (1988): <a href="Morris_worm" title="Morris worm">Morris worm</a></li>

<li>1988 (1988): Complete <a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a></li>

<li>1989 (1989): <a href="Border_Gateway_Protocol" title="Border Gateway Protocol">Border Gateway Protocol</a> (BGP)</li>

<li>1989 (1989): <a href="PSINet" title="PSINet">PSINet</a> founded, allows commercial traffic</li>

<li>1989 (1989): <a href="Federal_Internet_Exchange" title="Federal Internet Exchange">Federal Internet Exchanges (FIX East|FIXes)</a></li>

<li>1990 (1990): <a href="Government_Open_Systems_Interconnection_Profile" title="Government Open Systems Interconnection Profile">GOSIP</a> (without <a href="Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a>)</li>

<li>1990 (1990): ARPANET decommissioned</li>

<li>1990 (1990): <a href="Advanced_Network_and_Services" title="Advanced Network and Services">Advanced Network and Services</a> (ANS)</li>

<li>1991 (1991): <a href="Wide_area_information_server" title="Wide area information server">Wide area information server</a> (WAIS)</li>

<li>1991 (1991): <a href="Gopher_(protocol)" title="Gopher (protocol)">Gopher</a></li>

<li>1991 (1991): <a href="Commercial_Internet_eXchange" title="Commercial Internet eXchange">Commercial Internet eXchange</a> (CIX)</li>

<li>1991 (1991): <a href="Advanced_Network_and_Services" title="Advanced Network and Services">ANS CO+RE</a> allows commercial traffic</li>

<li>1991 (1991): <a href="World_Wide_Web" title="World Wide Web">World Wide Web</a> (WWW)</li>

<li>1992 (1992): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> upgraded to 45 Mbit/s (T3)</li>

<li>1992 (1992): <a href="Internet_Society" title="Internet Society">Internet Society</a> (ISOC) established</li>

<li>1993 (1993): <a href="Classless_Inter-Domain_Routing" title="Classless Inter-Domain Routing">Classless Inter-Domain Routing</a> (CIDR)</li>

<li>1993 (1993): <a href="InterNIC" title="InterNIC">InterNIC</a> established</li>

<li>1993 (1993): <a href="AOL" title="AOL">AOL</a> added <a href="Usenet" title="Usenet">USENET</a> access</li>

<li>1993 (1993): <a href="NCSA_Mosaic" title="NCSA Mosaic">Mosaic web browser</a> released</li>

<li>1994 (1994): <a href="Search_engine" title="Search engine">Full text web search engines</a></li>

<li>1994 (1994): <a href="North_American_Network_Operators'_Group" title="North American Network Operators' Group">North American Network Operators' Group</a> (NANOG) established</li></ul>

Commercialization, privatization, broader access leads to the modern Internet:

<ul><li>1995 (1995): New Internet architecture with commercial <a href="Internet_service_provider" title="Internet service provider">ISPs</a> connected at <a href="Network_Access_Point" class="mw-redirect" title="Network Access Point">NAPs</a></li>

<li>1995 (1995): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> decommissioned</li>

<li>1995 (1995): <a href="GOSIP" class="mw-redirect" title="GOSIP">GOSIP</a> updated to allow <a href="Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a></li>

<li>1995 (1995): <a href="Very_high-speed_Backbone_Network_Service" title="Very high-speed Backbone Network Service">very high-speed Backbone Network Service (vBNS)</a></li>

<li>1996 (1996): <a href="AOL" title="AOL">AOL</a> changes pricing model from hourly to monthly</li>

<li>1998 (1998): <a href="ICANN" title="ICANN">Internet Corporation for Assigned Names and Numbers (ICANN)</a></li>

<li>1999 (1999): <a href="IEEE_802.11" title="IEEE 802.11">IEEE 802.11b</a> wireless networking</li>

<li>1999 (1999): <a href="Internet2" title="Internet2">Internet2</a>/<a href="Abilene_Network" title="Abilene Network">Abilene Network</a></li>

<li>1999 (1999): <a href="VBNS" class="mw-redirect" title="VBNS">vBNS+</a> allows broader access</li>

<li>2000 (2000): <a href="Dot-com_bubble" title="Dot-com bubble">Dot-com bubble</a> bursts</li>

<li>2001 (2001): <a href="Top-level_domain#Proposed_domains" title="Top-level domain">New top-level domain names activated</a></li>

<li>2001 (2001): <a href="Code_Red_(computer_worm)" title="Code Red (computer worm)">Code Red I</a>, <a href="Code_Red_II" title="Code Red II">Code Red II</a>, and <a href="Nimda" title="Nimda">Nimda</a> worms</li>

<li>2003 (2003): <a href="World_Summit_on_the_Information_Society" title="World Summit on the Information Society">UN World Summit on the Information Society (WSIS) phase I</a></li></ul>

<ul><li>2003 (2003): <a href="National_LambdaRail" title="National LambdaRail">National LambdaRail</a> founded</li>

<li>2004 (2004): <a href="Working_Group_on_Internet_Governance" title="Working Group on Internet Governance">UN Working Group on Internet Governance (WGIG)</a></li>

<li>2005 (2005): <a href="World_Summit_on_the_Information_Society" title="World Summit on the Information Society">UN WSIS phase II</a></li>

<li>2006 (2006): <a href="Internet_Governance_Forum" title="Internet Governance Forum">First meeting of the Internet Governance Forum</a></li>

<li>2010 (2010): <a href="Top-level_domain#Internationalized_country_code_TLDs" title="Top-level domain">First internationalized country code top-level domains</a> registered</li>

<li>2012 (2012): <a href="Generic_top-level_domain#New_top-level_domains" title="Generic top-level domain">ICANN begins accepting applications for new generic top-level domain names</a></li>

<li>2013 (2013): <a href="Montevideo_Statement_on_the_Future_of_Internet_Cooperation" title="Montevideo Statement on the Future of Internet Cooperation">Montevideo Statement on the Future of Internet Cooperation</a></li>

<li>2014 (2014): <a href="NetMundial_Initiative" title="NetMundial Initiative">NetMundial international Internet governance proposal</a></li>

<li>2016 (2016): <a href="ICANN" title="ICANN">ICANN</a> contract with U.S. Dept. of Commerce ends, <a href="Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">IANA</a> oversight passes to the global Internet community on October 1st</li></ul>

Examples of Internet services:

<ul><li>1989 (1989): <a href="AOL" title="AOL">AOL</a> dial-up service provider, email, instant messaging, and web browser</li>

<li>1995 (1995): <a href="Amazon_(company)" title="Amazon (company)">Amazon</a> online retailer</li>

<li>1995 (1995): <a href="EBay" title="EBay">eBay</a> online auction and shopping</li>

<li>1995 (1995): <a href="Craigslist" title="Craigslist">Craigslist</a> classified advertisements</li>

<li>1995 (1995): <a href="AltaVista" title="AltaVista">AltaVista</a> search engine</li>

<li>1996 (1996): <a href="Outlook.com" title="Outlook.com">Outlook (formerly Hotmail)</a> free web-based e-mail</li>

<li>1996 (1996): <a href="Baidu" title="Baidu">RankDex</a> search engine</li>

<li>1997 (1997): <a href="Google_Search" title="Google Search">Google Search</a></li>

<li>1997 (1997): <a href="Babel_Fish_(website)" title="Babel Fish (website)">Babel Fish</a> automatic translation</li>

<li>1998 (1998): <a href="Yahoo_Groups" title="Yahoo Groups">Yahoo Groups (formerly Yahoo! Clubs)</a></li>

<li>1998 (1998): <a href="PayPal" title="PayPal">PayPal</a> Internet payment system</li>

<li>1998 (1998): <a href="Rotten_Tomatoes" title="Rotten Tomatoes">Rotten Tomatoes</a> review aggregator</li>

<li>1999 (1999): <a href="2channel" title="2channel">2ch</a> Anonymous textboard</li>

<li>1999 (1999): <a href="I-mode" title="I-mode">i-mode</a> mobile internet service</li>

<li>1999 (1999): <a href="Napster" title="Napster">Napster</a> peer-to-peer file sharing</li>

<li>2000 (2000): <a href="Baidu" title="Baidu">Baidu</a> search engine</li>

<li>2003 (2003): <a href="LinkedIn" title="LinkedIn">LinkedIn</a> business networking</li>

<li>2003 (2003): <a href="Myspace" title="Myspace">Myspace</a> social networking site</li>

<li>2003 (2003): <a href="The_Pirate_Bay" title="The Pirate Bay">The Pirate Bay</a>, <a href="Torrent_file" title="Torrent file">torrent file</a> host</li>

<li>2004 (2004): <a href="Facebook" title="Facebook">Facebook</a> social networking site</li>

<li>2004 (2004): <a href="Podcast" title="Podcast">Podcast</a> media file series</li>

<li>2004 (2004): <a href="Flickr" title="Flickr">Flickr</a> image hosting</li>

<li>2005 (2005): <a href="YouTube" title="YouTube">YouTube</a> video sharing</li>

<li>2005 (2005): <a href="Reddit" title="Reddit">Reddit</a> link voting</li>

<li>2005 (2005): <a href="Google_Earth" title="Google Earth">Google Earth</a> virtual globe</li>

<li>2006 (2006): <a href="Twitter" title="Twitter">Twitter</a> microblogging</li>

<li>2007 (2007): <a href="WikiLeaks" title="WikiLeaks">WikiLeaks</a> anonymous news and information leaks</li>

<li>2007 (2007): <a href="Google_Street_View" title="Google Street View">Google Street View</a></li>

<li>2007 (2007): <a href="Amazon_Kindle" title="Amazon Kindle">Kindle</a>, <a href="E-reader" title="E-reader">e-reader</a> and virtual bookshop</li>

<li>2008 (2008): <a href="Amazon_Elastic_Compute_Cloud" title="Amazon Elastic Compute Cloud">Amazon Elastic Compute Cloud</a> (EC2)</li>

<li>2008 (2008): <a href="Dropbox" title="Dropbox">Dropbox</a> cloud-based file hosting</li>

<li>2008 (2008): <a href="Encyclopedia_of_Life" title="Encyclopedia of Life">Encyclopedia of Life</a>, a collaborative encyclopedia intended to document all living species</li>

<li>2008 (2008): <a href="Spotify" title="Spotify">Spotify</a>, a <a href="Digital_rights_management" title="Digital rights management">DRM-based</a> music streaming service</li>

<li>2009 (2009): <a href="Microsoft_Bing" title="Microsoft Bing">Bing</a> search engine</li>

<li>2009 (2009): <a href="Google_Docs" title="Google Docs">Google Docs</a>, Web-based word processor, spreadsheet, presentation, form, and data storage service</li>

<li>2009 (2009): <a href="Kickstarter" title="Kickstarter">Kickstarter</a>, a <a href="Threshold_pledge_system" title="Threshold pledge system">threshold pledge system</a></li>

<li>2009 (2009): <a href="Bitcoin" title="Bitcoin">Bitcoin</a>, a <a href="Digital_currency" title="Digital currency">digital currency</a></li>

<li>2010 (2010): <a href="Instagram" title="Instagram">Instagram</a>, <a href="Photo_sharing" class="mw-redirect" title="Photo sharing">photo sharing</a> and <a href="Social_networking" class="mw-redirect" title="Social networking">social networking</a></li>

<li>2011 (2011): <a href="Google%2B" title="Google+">Google+</a>, <a href="Social_networking" class="mw-redirect" title="Social networking">social networking</a></li>

<li>2011 (2011): <a href="Snapchat" title="Snapchat">Snapchat</a>, <a href="Photo_sharing" class="mw-redirect" title="Photo sharing">photo sharing</a></li>

<li>2012 (2012): <a href="Coursera" title="Coursera">Coursera</a>, massive open online courses</li>

<li>2016 (2016): <a href="TikTok" title="TikTok">TikTok</a>, <a href="Video_sharing" class="mw-redirect" title="Video sharing">video sharing</a> and <a href="Social_networking" class="mw-redirect" title="Social networking">social networking</a></li></ul>

</td></tr></tbody></table>

The Internet Protocol (IP) is the <a href="Network_layer" title="Network layer">network layer</a> <a href="Communications_protocol" class="mw-redirect" title="Communications protocol">communications protocol</a> in the <a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a> for relaying <a href="Datagram" title="Datagram">datagrams</a> across network boundaries. Its <a href="Routing" title="Routing">routing</a> function enables <a href="Internetworking" title="Internetworking">internetworking</a>, and essentially establishes the <a href="Internet" title="Internet">Internet</a>.

IP has the task of delivering <a href="Packet_(information_technology)" class="mw-redirect" title="Packet (information technology)">packets</a> from the source <a href="Host_(network)" title="Host (network)">host</a> to the destination host solely based on the <a href="IP_address" title="IP address">IP addresses</a> in the packet <a href="Header_(computing)" title="Header (computing)">headers</a>. For this purpose, IP defines packet structures that <a href="Encapsulation_(networking)" title="Encapsulation (networking)">encapsulate</a> the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information.

IP was the <a href="Connectionless" class="mw-redirect" title="Connectionless">connectionless</a> datagram service in the original <a href="Transmission_Control_Program" class="mw-redirect" title="Transmission Control Program">Transmission Control Program</a> introduced by <a href="Vint_Cerf" title="Vint Cerf">Vint Cerf</a> and <a href="Bob_Kahn" class="mw-redirect" title="Bob Kahn">Bob Kahn</a> in 1974, which was complemented by a <a href="Connection-oriented" class="mw-redirect" title="Connection-oriented">connection-oriented</a> service that became the basis for the <a href="Transmission_Control_Protocol" title="Transmission Control Protocol">Transmission Control Protocol</a> (TCP). The Internet protocol suite is therefore often referred to as TCP/IP.

The first major version of IP, <a href="Internet_Protocol_version_4" class="mw-redirect" title="Internet Protocol version 4">Internet Protocol version 4</a> (IPv4), is the dominant protocol of the Internet. Its successor is <a href="Internet_Protocol_version_6" class="mw-redirect" title="Internet Protocol version 6">Internet Protocol version 6</a> (IPv6), which has been in increasing <a href="IPv6_deployment" title="IPv6 deployment">deployment</a> on the public Internet since around 2006.<a href="#cite_note-1">[1]</a>

<div class="mw-heading mw-heading2"><h2 id="Function">Function</h2></div>

The Internet Protocol is responsible for addressing <a href="Host_interface" class="mw-redirect" title="Host interface">host interfaces</a>, encapsulating data into datagrams (including <a href="IP_fragmentation" title="IP fragmentation">fragmentation and reassembly</a>) and routing datagrams from a source host interface to a destination host interface across one or more IP networks.<a href="#cite_note-2">[2]</a> For these purposes, the Internet Protocol defines the format of packets and provides an addressing system.

Each datagram has two components: a <a href="Header_(computing)" title="Header (computing)">header</a> and a <a href="Payload_(computing)" title="Payload (computing)">payload</a>. The <a href="IP_header" title="IP header">IP header</a> includes a source IP address, a destination IP address, and other metadata needed to route and deliver the datagram. The payload is the data that is transported. This method of nesting the data payload in a packet with a header is called encapsulation.

IP addressing entails the assignment of IP addresses and associated parameters to host interfaces. The address space is divided into <a href="Subnet" title="Subnet">subnets</a>, involving the designation of network prefixes. IP routing is performed by all hosts, as well as <a href="Router_(computing)" title="Router (computing)">routers</a>, whose main function is to transport packets across network boundaries. Routers communicate with one another via specially designed <a href="Routing_protocol" title="Routing protocol">routing protocols</a>, either <a href="Interior_gateway_protocol" title="Interior gateway protocol">interior gateway protocols</a> or <a href="Exterior_gateway_protocol" title="Exterior gateway protocol">exterior gateway protocols</a>, as needed for the topology of the network.<a href="#cite_note-3">[3]</a>

<div class="mw-heading mw-heading2"><h2 id="Addressing_methods">Addressing methods</h2></div>

<th style="background-color:#ddd; color:#00F12; border-bottom:thin solid #999;"><a href="Routing#Delivery_schemes" title="Routing">Routing schemes</a>

</th></tr>

<tr>

<th style="border-bottom:thin solid #999;"><a href="Unicast" title="Unicast">Unicast</a>

</th></tr>

<tr>

<th style="border-bottom:thin solid #999;"><a href="Broadcasting_(networking)" title="Broadcasting (networking)">Broadcast</a>

</th></tr>

<tr>

<th style="border-bottom:thin solid #999;"><a href="Multicast" title="Multicast">Multicast</a>

</th></tr>

<tr>

<th><a href="Anycast" title="Anycast">Anycast</a>

</th></tr></tbody></table>

There are four principal addressing methods in the Internet Protocol:

<ul><li><a href="Unicast" title="Unicast">Unicast</a> delivers a message to a single specific node using a one-to-one association between a sender and destination: each destination address uniquely identifies a single receiver endpoint.</li>

<li><a href="Broadcasting_(networking)" title="Broadcasting (networking)">Broadcast</a> delivers a message to all nodes in the network using a one-to-all association; a single <a href="Datagram" title="Datagram">datagram</a> (or <a href="Packet_(information_technology)" class="mw-redirect" title="Packet (information technology)">packet</a>) from one sender is routed to all of the possibly multiple endpoints associated with the <a href="Broadcast_address" title="Broadcast address">broadcast address</a>. The network automatically replicates datagrams as needed to reach all the recipients within the scope of the broadcast, which is generally an entire network <a href="Subnetwork" class="mw-redirect" title="Subnetwork">subnet</a>.</li>

<li><a href="Multicast" title="Multicast">Multicast</a> delivers a message to a group of nodes that have expressed interest in receiving the message using a one-to-many-of-many or many-to-many-of-many association; datagrams are routed simultaneously in a single transmission to many recipients. Multicast differs from broadcast in that the destination address designates a subset, not necessarily all, of the accessible nodes.</li>

<li><a href="Anycast" title="Anycast">Anycast</a> delivers a message to any one out of a group of nodes, typically the one nearest to the source using a one-to-one-of-many<a href="#cite_note-4">[4]</a> association where datagrams are routed to any single member of a group of potential receivers that are all identified by the same destination address. The routing algorithm selects the single receiver from the group based on which is the nearest according to some distance or cost measure.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Version_history">Version history</h2></div>

In May 1974, the <a href="Institute_of_Electrical_and_Electronics_Engineers" title="Institute of Electrical and Electronics Engineers">Institute of Electrical and Electronics Engineers</a> (IEEE) published a paper entitled "A Protocol for Packet Network Intercommunication".<a href="#cite_note-5">[5]</a> The paper's authors, <a href="Vint_Cerf" title="Vint Cerf">Vint Cerf</a> and <a href="Bob_Kahn" class="mw-redirect" title="Bob Kahn">Bob Kahn</a>, described an <a href="Internetworking" title="Internetworking">internetworking</a> protocol for sharing resources using <a href="Packet_switching" title="Packet switching">packet switching</a> among <a href="Network_node" class="mw-redirect" title="Network node">network nodes</a>. A central control component of this model was the Transmission Control Program that incorporated both connection-oriented links and datagram services between hosts. The monolithic Transmission Control Program was later divided into a modular architecture consisting of the <a href="Transmission_Control_Protocol" title="Transmission Control Protocol">Transmission Control Protocol</a> and <a href="User_Datagram_Protocol" title="User Datagram Protocol">User Datagram Protocol</a> at the <a href="Transport_layer" title="Transport layer">transport layer</a> and the Internet Protocol at the <a href="Internet_layer" title="Internet layer">internet layer</a>. The model became known as the Department of Defense (DoD) Internet Model and <a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a>, and informally as TCP/IP.

The following <a href="Internet_Experiment_Note" title="Internet Experiment Note">Internet Experiment Note</a> (IEN) documents describe the evolution of the Internet Protocol into the modern version of IPv4:<a href="#cite_note-6">[6]</a>

<ul><li><a rel="nofollow" class="external text" href="http://www.rfc-editor.org/ien/ien2.txt">IEN 2</a> Comments on Internet Protocol and TCP (August 1977) describes the need to separate the TCP and Internet Protocol functionalities (which were previously combined). It proposes the first version of the IP header, using 0 for the version field.</li>

<li><a rel="nofollow" class="external text" href="http://www.rfc-editor.org/ien/ien26.pdf">IEN 26</a> A Proposed New Internet Header Format (February 1978) describes a version of the IP header that uses a 1-bit version field.</li>

<li><a rel="nofollow" class="external text" href="http://www.rfc-editor.org/ien/ien28.pdf">IEN 28</a> Draft Internetwork Protocol Description Version 2 (February 1978) describes IPv2.</li>

<li><a rel="nofollow" class="external text" href="http://www.rfc-editor.org/ien/ien41.pdf">IEN 41</a> Internetwork Protocol Specification Version 4 (June 1978) describes the first protocol to be called IPv4. The IP header is different from the modern IPv4 header.</li>

<li><a rel="nofollow" class="external text" href="http://www.rfc-editor.org/ien/ien44.pdf">IEN 44</a> Latest Header Formats (June 1978) describes another version of IPv4, also with a header different from the modern IPv4 header.</li>

<li><a rel="nofollow" class="external text" href="http://www.rfc-editor.org/ien/ien54.pdf">IEN 54</a> Internetwork Protocol Specification Version 4 (September 1978) is the first description of IPv4 using the header that would become standardized in 1980 as <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc760">760</a>.</li>

IP versions 1 to 3 were experimental versions, designed between 1973 and 1978.<a href="#cite_note-Coty-7">[7]</a> Versions 2 and 3 supported variable-length addresses ranging between 1 and 16 octets (between 8 and 128 bits).<a href="#cite_note-8">[8]</a> An early draft of version 4 supported variable-length addresses of up to 256 octets (up to 2048 bits)<a href="#cite_note-9">[9]</a> but this was later abandoned in favor of a fixed-size 32-bit address in the final version of <a href="IPv4" title="IPv4">IPv4</a>. This remains the dominant internetworking protocol in use in the <a href="Internet_Layer" class="mw-redirect" title="Internet Layer">Internet Layer</a>; the number 4 identifies the protocol version, carried in every IP datagram. IPv4 is defined in <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc791">791</a> (1981).

Version number 5 was used by the <a href="Internet_Stream_Protocol" title="Internet Stream Protocol">Internet Stream Protocol</a>, an experimental streaming protocol that was not adopted.<a href="#cite_note-Coty-7">[7]</a>

The successor to IPv4 is <a href="IPv6" title="IPv6">IPv6</a>. IPv6 was a result of several years of experimentation and dialog during which various protocol models were proposed, such as TP/IX (<a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1475">1475</a>), PIP (<a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1621">1621</a>) and TUBA (TCP and UDP with Bigger Addresses, <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1347">1347</a>). Its most prominent difference from version 4 is the size of the addresses. While IPv4 uses <a href="32_bits" class="mw-redirect" title="32 bits">32 bits</a> for addressing, yielding c. 4.3 <a href="1%2C000%2C000%2C000_(number)" class="mw-redirect" title="1,000,000,000 (number)">billion</a> (4.3×109) addresses, IPv6 uses <a href="128-bit" class="mw-redirect" title="128-bit">128-bit</a> addresses providing c. 3.4×1038 addresses. Although adoption of IPv6 has been slow, as of January 2023, most countries in the world show significant adoption of IPv6,<a href="#cite_note-10">[10]</a> with over 41% of Google's traffic being carried over IPv6 connections.<a href="#cite_note-11">[11]</a>

The assignment of the new protocol as IPv6 was uncertain until due diligence assured that IPv6 had not been used previously.<a href="#cite_note-12">[12]</a> Other Internet Layer protocols have been assigned version numbers,<a href="#cite_note-13">[13]</a> such as 7 (IP/TX), 8 and 9 (historic). Notably, on April 1, 1994, the <a href="IETF" class="mw-redirect" title="IETF">IETF</a> published an <a href="April_Fools'_Day_RfC" class="mw-redirect" title="April Fools' Day RfC">April Fools' Day RfC</a> about IPv9.<a href="#cite_note-14">[14]</a> IPv9 was also used in an alternate proposed address space expansion called TUBA.<a href="#cite_note-15">[15]</a> A 2004 Chinese proposal for <a href="IPv9_(China)" title="IPv9 (China)">an IPv9 protocol</a> appears to be unrelated to all of these, and is not endorsed by the IETF.

<div class="mw-heading mw-heading3"><h3 id="IP_version_numbers">IP version numbers</h3></div>

As the version number is carried in a 4-bit field, only numbers 0–15 can be assigned.

<th>IP version

</th>

<th>Description

</th>

<th>Year

</th>

<th>Status

</th></tr>

<tr>

<th>0

</th>

<td>Internet Protocol, pre-v4</td>

<td>Reserved<a href="#cite_note-routing_tcp/ip-16">[16]</a>

</td></tr>

<tr>

<th>1

</th>

<td>Experimental version</td>

<td>Obsolete

</td></tr>

<tr>

<th>2

</th>

<td>Experimental version</td>

<td>Obsolete

</td></tr>

<tr>

<th>3

</th>

<td>Experimental version</td>

<td>Obsolete

</td></tr>

<tr>

<th>4

</th>

<td><a href="Internet_Protocol_version_4" class="mw-redirect" title="Internet Protocol version 4">Internet Protocol version 4</a> (IPv4)<a href="#cite_note-rfc791-17">[17]</a></td>

<td>Active

</td></tr>

<tr>

<th rowspan="3">5

</th>

<td><a href="Internet_Stream_Protocol" title="Internet Stream Protocol">Internet Stream Protocol</a> (ST)</td>

<td>Obsolete; superseded by ST-II or ST2

</td></tr>

<tr>

<td><a href="Internet_Stream_Protocol" title="Internet Stream Protocol">Internet Stream Protocol</a> (ST-II or ST2)<a href="#cite_note-rfc1819-18">[18]</a></td>

<td>Obsolete; superseded by ST2+

</td></tr>

<tr>

<td><a href="Internet_Stream_Protocol" title="Internet Stream Protocol">Internet Stream Protocol</a> (ST2+)</td>

<td>Obsolete

</td></tr>

<tr>

<th rowspan="2">6

</th>

<td>Simple Internet Protocol (SIP)</td>

<td>Obsolete; merged into IPv6 in 1995<a href="#cite_note-routing_tcp/ip-16">[16]</a>

</td></tr>

<tr>

<td><a href="Internet_Protocol_version_6" class="mw-redirect" title="Internet Protocol version 6">Internet Protocol version 6</a> (IPv6)<a href="#cite_note-rfc8200-19">[19]</a></td>

<td>Active

</td></tr>

<tr>

<th>7

</th>

<td>TP/IX The Next Internet (IPv7)<a href="#cite_note-rfc1475-20">[20]</a></td>

<td>Obsolete<a href="#cite_note-rfc6814-21">[21]</a>

</td></tr>

<tr>

<th>8

</th>

<td>P Internet Protocol (PIP)<a href="#cite_note-rfc1621-22">[22]</a></td>

<td>Obsolete; merged into SIP in 1993

</td></tr>

<tr>

<th rowspan="3">9

</th>

<td>TCP and UDP over Bigger Addresses (TUBA)</td>

<td>Obsolete<a href="#cite_note-rfc1347-23">[23]</a>

</td></tr>

<tr>

<td><a href="April_Fools'_Day" title="April Fools' Day">April Fools' Day</a> joke<a href="#cite_note-rfc1606-24">[24]</a>

</td></tr>

<tr>

<td><a href="Chinese_IPv9" class="mw-redirect" title="Chinese IPv9">Chinese IPv9</a></td>

<td>Abandoned

</td></tr>

<tr>

<th>10–14

</th>

<td>Unassigned

</td></tr>

<tr>

<th>15

</th>

<td>Version field sentinel value</td>

<td>Reserved

</td></tr></tbody></table>

<div class="mw-heading mw-heading2"><h2 id="Reliability">Reliability</h2></div>

The design of the Internet protocol suite adheres to the <a href="End-to-end_principle" title="End-to-end principle">end-to-end principle</a>, a concept adapted from the <a href="CYCLADES" title="CYCLADES">CYCLADES</a> project. Under the end-to-end principle, the network infrastructure is considered inherently unreliable at any single network element or transmission medium and is dynamic in terms of the availability of links and nodes. No central monitoring or performance measurement facility exists that tracks or maintains the state of the network. For the benefit of reducing <a href="Network_complexity" title="Network complexity">network complexity</a>, the intelligence in the network is located in the <a href="End_node" class="mw-redirect" title="End node">end nodes</a>.

As a consequence of this design, the Internet Protocol only provides <a href="Best-effort_delivery" title="Best-effort delivery">best-effort delivery</a> and its service is characterized as <a href="Reliability_(computer_networking)" title="Reliability (computer networking)">unreliable</a>. In network architectural parlance, it is a <a href="Connectionless_protocol" class="mw-redirect" title="Connectionless protocol">connectionless protocol</a>, in contrast to <a href="Connection-oriented_communication" title="Connection-oriented communication">connection-oriented communication</a>. Various fault conditions may occur, such as <a href="Data_corruption" title="Data corruption">data corruption</a>, <a href="Packet_loss" title="Packet loss">packet loss</a> and duplication. Because routing is dynamic, meaning every packet is treated independently, and because the network maintains no state based on the path of prior packets, different packets may be routed to the same destination via different paths, resulting in <a href="Out-of-order_delivery" title="Out-of-order delivery">out-of-order delivery</a> to the receiver.

All fault conditions in the network must be detected and compensated by the participating end nodes. The <a href="Upper_layer_protocol" class="mw-redirect" title="Upper layer protocol">upper layer protocols</a> of the Internet protocol suite are responsible for resolving reliability issues. For example, a host may <a href="Data_buffer" title="Data buffer">buffer</a> network data to ensure correct ordering before the data is delivered to an application.

IPv4 provides safeguards to ensure that the header of an IP packet is error-free. A routing node discards packets that fail a header <a href="Checksum" title="Checksum">checksum</a> test. Although the <a href="Internet_Control_Message_Protocol" title="Internet Control Message Protocol">Internet Control Message Protocol</a> (ICMP) provides notification of errors, a routing node is not required to notify either end node of errors. IPv6, by contrast, operates without header checksums, since current <a href="Link_layer" title="Link layer">link layer</a> technology is assumed to provide sufficient error detection.<a href="#cite_note-25">[25]</a><a href="#cite_note-26">[26]</a>

<div class="mw-heading mw-heading2"><h2 id="Link_capacity_and_capability">Link capacity and capability</h2></div>

The dynamic nature of the Internet and the diversity of its components provide no guarantee that any particular path is actually capable of, or suitable for, performing the data transmission requested. One of the technical constraints is the size of data packets possible on a given link. Facilities exist to examine the <a href="Maximum_transmission_unit" title="Maximum transmission unit">maximum transmission unit</a> (MTU) size of the local link and <a href="Path_MTU_Discovery" title="Path MTU Discovery">Path MTU Discovery</a> can be used for the entire intended path to the destination.<a href="#cite_note-27">[27]</a>

The IPv4 internetworking layer automatically <a href="IP_fragmentation" title="IP fragmentation">fragments</a> a datagram into smaller units for transmission when the link MTU is exceeded. IP provides re-ordering of fragments received out of order.<a href="#cite_note-28">[28]</a> An IPv6 network does not perform fragmentation in network elements, but requires end hosts and higher-layer protocols to avoid exceeding the path MTU.<a href="#cite_note-29">[29]</a>

The <a href="Transmission_Control_Protocol" title="Transmission Control Protocol">Transmission Control Protocol</a> (TCP) is an example of a protocol that adjusts its segment size to be smaller than the MTU. The <a href="User_Datagram_Protocol" title="User Datagram Protocol">User Datagram Protocol</a> (UDP) and ICMP disregard MTU size, thereby forcing IP to fragment oversized datagrams.<a href="#cite_note-30">[30]</a>

<div class="mw-heading mw-heading2"><h2 id="Security">Security</h2></div>

During the design phase of the <a href="ARPANET" title="ARPANET">ARPANET</a> and the early Internet, the security aspects and needs of a public, international network were not adequately anticipated. Consequently, many Internet protocols exhibited vulnerabilities highlighted by network attacks and later security assessments. In 2008, a thorough security assessment and proposed mitigation of problems was published.<a href="#cite_note-31">[31]</a> The IETF has been pursuing further studies.<a href="#cite_note-RFC_6274-32">[32]</a>

/* start https://en.wikipedia.org/ */

.mw-parser-output .portalbox{padding:0;margin:0.5em 0;display:table;box-sizing:border-box;max-width:175px;list-style:none}.mw-parser-output .portalborder{border:1px solid var(--border-color-base,#a2a9b1);padding:0.1em;background:var(--background-color-neutral-subtle,#f8f9fa)}.mw-parser-output .portalbox-entry{display:table-row;font-size:85%;line-height:110%;height:1.9em;font-style:italic;font-weight:bold}.mw-parser-output .portalbox-image{display:table-cell;padding:0.2em;vertical-align:middle;text-align:center}.mw-parser-output .portalbox-link{display:table-cell;padding:0.2em 0.2em 0.2em 0.3em;vertical-align:middle}@media(min-width:720px){.mw-parser-output .portalleft{margin:0.5em 1em 0.5em 0}.mw-parser-output .portalright{clear:right;float:right;margin:0.5em 0 0.5em 1em}}

/* end https://en.wikipedia.org/ */

</style>

<ul><li><a href="ICANN" title="ICANN">ICANN</a></li>

<li><a href="IP_routing" title="IP routing">IP routing</a></li>

<li><a href="List_of_IP_protocol_numbers" title="List of IP protocol numbers">List of IP protocol numbers</a></li>

<li><a href="List_of_IP_version_numbers" title="List of IP version numbers">List of IP version numbers</a></li>

<li><a href="Next-generation_network" title="Next-generation network">Next-generation network</a></li>

<li><a href="New_IP" title="New IP">New IP</a> (proposal)</li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-1"><a href="#cite_ref-1">^</a> <cite class="citation report cs1"><a rel="nofollow" class="external text" href="https://www.oecd-ilibrary.org/science-and-technology/the-economics-of-transition-to-internet-protocol-version-6-ipv6_5jxt46d07bhc-en">The Economics of Transition to Internet Protocol version 6 (IPv6)</a> (Report). OECD Digital Economy Papers. OECD. 2014-11-06. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1787%2F5jxt46d07bhc-en">10.1787/5jxt46d07bhc-en</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210307213313/https://www.oecd-ilibrary.org/science-and-technology/the-economics-of-transition-to-internet-protocol-version-6-ipv6_5jxt46d07bhc-en">Archived</a> from the original on 2021-03-07. Retrieved 2020-12-04.</cite>

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <cite id="CITEREFCharles_M._Kozierok" class="citation cs2">Charles M. Kozierok, <a rel="nofollow" class="external text" href="http://www.tcpipguide.com/free/t_IPFunctions.htm">The TCP/IP Guide</a>, <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190620010402/http://www.tcpipguide.com/free/t_IPFunctions.htm">archived</a> from the original on 2019-06-20, retrieved 2017-07-22</cite>

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20210105023938/http://www.eitc.org/research-opportunities/future-internet-and-optical-quantum-communications/internet-networks-and-tcp-ip/ip-technologies-and-migration">"IP Technologies and Migration — EITC"</a>. www.eitc.org. Archived from <a rel="nofollow" class="external text" href="http://www.eitc.org/research-opportunities/future-internet-and-optical-quantum-communications/internet-networks-and-tcp-ip/ip-technologies-and-migration">the original</a> on 2021-01-05. Retrieved 2020-12-04.</cite>

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite id="CITEREFGościeńWalkowiakKlinkowski2015" class="citation journal cs1">Goścień, Róża; Walkowiak, Krzysztof; Klinkowski, Mirosław (2015-03-14). <a rel="nofollow" class="external text" href="https://www.sciencedirect.com/science/article/pii/S1389128614004460">"Tabu search algorithm for routing, modulation and spectrum allocation in elastic optical network with anycast and unicast traffic"</a>. Computer Networks. 79: 148–165. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.comnet.2014.12.004">10.1016/j.comnet.2014.12.004</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1389-1286">1389-1286</a>.</cite>

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite id="CITEREFCerfKahn1974" class="citation journal cs1">Cerf, V.; Kahn, R. (1974). <a rel="nofollow" class="external text" href="https://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf">"A Protocol for Packet Network Intercommunication"</a> (PDF). IEEE Transactions on Communications. 22 (5): 637–648. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTCOM.1974.1092259">10.1109/TCOM.1974.1092259</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1558-0857">1558-0857</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170106204542/http://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf">Archived</a> (PDF) from the original on 2017-01-06. Retrieved 2020-04-06. <q>The authors wish to thank a number of colleagues for helpful comments during early discussions of international network protocols, especially R. Metcalfe, R. Scantlebury, D. Walden, and H. Zimmerman; D. Davies and L. Pouzin who constructively commented on the fragmentation and accounting issues; and S. Crocker who commented on the creation and destruction of associations.</q></cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.rfc-editor.org/ien/ien-index.html">"Internet Experiment Note Index"</a>. www.rfc-editor.org. Retrieved 2024-01-21.</cite>

</li>

<li id="cite_note-Coty-7">^ <a href="#cite_ref-Coty_7-0">a</a> <a href="#cite_ref-Coty_7-1">b</a> <cite id="CITEREFStephen_Coty2011" class="citation web cs1">Stephen Coty (2011-02-11). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200802011845/https://blog.alertlogic.com/blog/where-is-ipv1,-2,-3,and-5/">"Where is IPv1, 2, 3, and 5?"</a>. Archived from <a rel="nofollow" class="external text" href="https://blog.alertlogic.com/blog/where-is-ipv1,-2,-3,and-5/">the original</a> on 2020-08-02. Retrieved 2020-03-25.</cite>

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> <cite id="CITEREFPostel1978" class="citation cs1">Postel, Jonathan B. (February 1978). <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/ien/ien28.pdf">"Draft Internetwork Protocol Specification Version 2"</a> (PDF). RFC Editor. IEN 28. Retrieved 6 October 2022.</cite> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190516090051/https://www.rfc-editor.org/ien/ien28.pdf">Archived</a> 16 May 2019 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite id="CITEREFPostel1978" class="citation cs1">Postel, Jonathan B. (June 1978). <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/ien/ien41.pdf">"Internetwork Protocol Specification Version 4"</a> (PDF). RFC Editor. IEN 41. Retrieved 11 February 2024.</cite> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190516090053/http://www.rfc-editor.org/ien/ien41.pdf">Archived</a> 16 May 2019 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> <cite id="CITEREFStrowes2021" class="citation web cs1">Strowes, Stephen (4 Jun 2021). <a rel="nofollow" class="external text" href="https://labs.ripe.net/author/stephen_strowes/ipv6-adoption-in-2021/">"IPv6 Adoption in 2021"</a>. RIPE Labs. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210920213008/https://labs.ripe.net/author/stephen_strowes/ipv6-adoption-in-2021/">Archived</a> from the original on 2021-09-20. Retrieved 2021-09-20.</cite>

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption">"IPv6"</a>. Google. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200714184705/https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption">Archived</a> from the original on 2020-07-14. Retrieved 2023-05-19.</cite>

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> <cite id="CITEREFMulligan" class="citation web cs1">Mulligan, Geoff. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20150705060055/http://archive.oreilly.com/cs/user/view/cs_msg/25036">"It was almost IPv7"</a>. O'Reilly. Archived from <a rel="nofollow" class="external text" href="http://archive.oreilly.com/cs/user/view/cs_msg/25036">the original</a> on 5 July 2015. Retrieved 4 July 2015.</cite>

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.iana.org/assignments/version-numbers/version-numbers.xhtml">"IP Version Numbers"</a>. Internet Assigned Numbers Authority. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190118144623/https://www.iana.org/assignments/version-numbers/version-numbers.xhtml">Archived</a> from the original on 2019-01-18. Retrieved 2019-07-25.</cite>

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1606">1606</a>: A Historical Perspective On The Usage Of IP Version 9. April 1, 1994.

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite id="CITEREFRoss_Callon1992" class="citation cs1">Ross Callon (June 1992). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1347">TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1347">10.17487/RFC1347</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1347">1347</a>.</cite>

</li>

<li id="cite_note-routing_tcp/ip-16">^ <a href="#cite_ref-routing_tcp/ip_16-0">a</a> <a href="#cite_ref-routing_tcp/ip_16-1">b</a> <cite id="CITEREFJeff_DoyleJennifer_Carroll2006" class="citation book cs1">Jeff Doyle; Jennifer Carroll (2006). Routing TCP/IP. Vol. 1 (2 ed.). Cisco Press. p. 8. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-58705-202-6</bdi>.</cite>

</li>

<li id="cite_note-rfc791-17"><a href="#cite_ref-rfc791_17-0">^</a> <cite id="CITEREFJ._Postel1981" class="citation cs1"><a href="Jon_Postel" title="Jon Postel">J. Postel</a>, ed. (September 1981). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc791">INTERNET PROTOCOL - DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION</a>. <a href="IETF" class="mw-redirect" title="IETF">IETF</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC0791">10.17487/RFC0791</a>. STD 5. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc791">791</a>. IEN 128, 123, 111, 80, 54, 44, 41, 28, 26.</cite> Internet Standard 5. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc760">760</a>. Updated by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1349">1349</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2474">2474</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc6864">6864</a>.

</li>

<li id="cite_note-rfc1819-18"><a href="#cite_ref-rfc1819_18-0">^</a> <cite id="CITEREFL._DelgrossiL._Berger1995" class="citation cs1">L. Delgrossi; L. Berger, eds. (August 1995). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1819">Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+</a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1819">10.17487/RFC1819</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1819">1819</a>.</cite> Historic. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1190">1190</a> and IEN 119.

</li>

<li id="cite_note-rfc8200-19"><a href="#cite_ref-rfc8200_19-0">^</a> <cite id="CITEREFS._DeeringR._Hinden2017" class="citation cs1"><a href="Steve_Deering" title="Steve Deering">S. Deering</a>; R. Hinden (July 2017). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8200">Internet Protocol, Version 6 (IPv6) Specification</a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC8200">10.17487/RFC8200</a>. STD 86. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8200">8200</a>.</cite> Internet Standard 86. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2460">2460</a>.

</li>

<li id="cite_note-rfc1475-20"><a href="#cite_ref-rfc1475_20-0">^</a> <cite id="CITEREFR._Ullmann1993" class="citation cs1">R. Ullmann (June 1993). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1475">TP/IX: The Next Internet</a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1475">10.17487/RFC1475</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1475">1475</a>.</cite> Historic. Obsoleted by RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc6814">6814</a>.

</li>

<li id="cite_note-rfc6814-21"><a href="#cite_ref-rfc6814_21-0">^</a> <cite id="CITEREFC._PignataroF._Gont2012" class="citation cs1">C. Pignataro; F. Gont (November 2012). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6814">Formally Deprecating Some IPv4 Options</a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC6814">10.17487/RFC6814</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2070-1721">2070-1721</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6814">6814</a>.</cite> Proposed Standard. Obsoletes RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1385">1385</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1393">1393</a>, <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1475">1475</a> and <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1770">1770</a>.

</li>

<li id="cite_note-rfc1621-22"><a href="#cite_ref-rfc1621_22-0">^</a> <cite id="CITEREFP._Francis1994" class="citation cs1">P. Francis (May 1994). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1621">Pip Near-term Architecture</a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1621">10.17487/RFC1621</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1621">1621</a>.</cite> Historic.

</li>

<li id="cite_note-rfc1347-23"><a href="#cite_ref-rfc1347_23-0">^</a> <cite id="CITEREFRoss_Callon1992" class="citation cs1">Ross Callon (June 1992). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1347">TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing</a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1347">10.17487/RFC1347</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1347">1347</a>.</cite> Historic.

</li>

<li id="cite_note-rfc1606-24"><a href="#cite_ref-rfc1606_24-0">^</a> <cite id="CITEREFJ._Onions1994" class="citation cs1">J. Onions (1 April 1994). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1606">A Historical Perspective On The Usage Of IP Version 9</a>. Network Working Group. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1606">10.17487/RFC1606</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1606">1606</a>.</cite> Informational. This is an <a href="April_Fools'_Day_Request_for_Comments" title="April Fools' Day Request for Comments">April Fools' Day Request for Comments</a>.

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1726">1726</a> section 6.2

</li>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <cite id="CITEREFRishabh2012" class="citation book cs1">Rishabh, Anand (2012). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=XDJlDwAAQBAJ&q=The+dynamic+nature+of+the+Internet+and+the+diversity+of+its+components+provide+no+guarantee+that+any+particular+path+is+actually+capable+of%2C+or+suitable+for%2C+performing+the+data+transmission+requested.+One+of+the+technical+constraints+is+the+size+of+data+packets+possible+on+a+given+link.+Facilities+exist+to+examine+the+maximum+transmission+unit+%28MTU%29+size+of+the+local+link+and+Path+MTU+Discovery+can+be+used+for+the+entire+intended+path+to+the+destination.&pg=PA332">Wireless Communication</a>. S. Chand Publishing. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-81-219-4055-9</bdi>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240612133919/https://books.google.com/books?id=XDJlDwAAQBAJ&q=The+dynamic+nature+of+the+Internet+and+the+diversity+of+its+components+provide+no+guarantee+that+any+particular+path+is+actually+capable+of%2C+or+suitable+for%2C+performing+the+data+transmission+requested.+One+of+the+technical+constraints+is+the+size+of+data+packets+possible+on+a+given+link.+Facilities+exist+to+examine+the+maximum+transmission+unit+%28MTU%29+size+of+the+local+link+and+Path+MTU+Discovery+can+be+used+for+the+entire+intended+path+to+the+destination.&pg=PA332#v=snippet&q=The%20dynamic%20nature%20of%20the%20Internet%20and%20the%20diversity%20of%20its%20components%20provide%20no%20guarantee%20that%20any%20particular%20path%20is%20actually%20capable%20of%2C%20or%20suitable%20for%2C%20performing%20the%20data%20transmission%20requested.%20One%20of%20the%20technical%20constraints%20is%20the%20size%20of%20data%20packets%20possible%20on%20a%20given%20link.%20Facilities%20exist%20to%20examine%20the%20maximum%20transmission%20unit%20(MTU)%20size%20of%20the%20local%20link%20and%20Path%20MTU%20Discovery%20can%20be%20used%20for%20the%20entire%20intended%20path%20to%20the%20destination.&f=false">Archived</a> from the original on 2024-06-12. Retrieved 2020-12-11.</cite>

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> Siyan, Karanjit. Inside TCP/IP, New Riders Publishing, 1997. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-56205-714-6</bdi>

</li>

<li id="cite_note-29"><a href="#cite_ref-29">^</a> <cite id="CITEREFBill_Cerveny2011" class="citation web cs1">Bill Cerveny (2011-07-25). <a rel="nofollow" class="external text" href="https://www.arbornetworks.com/blog/asert/ipv6-fragmentation/">"IPv6 Fragmentation"</a>. <a href="Arbor_Networks" title="Arbor Networks">Arbor Networks</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160916162637/https://www.arbornetworks.com/blog/asert/ipv6-fragmentation/">Archived</a> from the original on 2016-09-16. Retrieved 2016-09-10.</cite>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <cite id="CITEREFParker2010" class="citation web cs1">Parker, Don (2 November 2010). <a rel="nofollow" class="external text" href="https://community.broadcom.com/symantecenterprise/communities/community-home/librarydocuments/viewdocument?DocumentKey=03c598ea-e171-47c9-8035-753ccd8bb36e&CommunityKey=1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68&tab=librarydocuments">"Basic Journey of a Packet"</a>. <a href="Broadcom#Symantec_enterprise_security" title="Broadcom">Symantec</a>. <a href="NortonLifeLock" class="mw-redirect" title="NortonLifeLock">Symantec</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220120044011/https://community.broadcom.com/symantecenterprise/communities/community-home/librarydocuments/viewdocument?DocumentKey=03c598ea-e171-47c9-8035-753ccd8bb36e&CommunityKey=1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68&tab=librarydocuments">Archived</a> from the original on 20 January 2022. Retrieved 4 May 2014.</cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite id="CITEREFFernando_Gont2008" class="citation cs2">Fernando Gont (July 2008), <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100211145721/http://www.cpni.gov.uk/Docs/InternetProtocol.pdf">Security Assessment of the Internet Protocol</a> (PDF), <a href="Centre_for_the_Protection_of_National_Infrastructure" class="mw-redirect" title="Centre for the Protection of National Infrastructure">CPNI</a>, archived from <a rel="nofollow" class="external text" href="http://www.cpni.gov.uk/Docs/InternetProtocol.pdf">the original</a> (PDF) on 2010-02-11</cite>

</li>

<li id="cite_note-RFC_6274-32"><a href="#cite_ref-RFC_6274_32-0">^</a> <cite id="CITEREFF._Gont2011" class="citation cs1">F. Gont (July 2011). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6274">Security Assessment of the Internet Protocol version 4</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC6274">10.17487/RFC6274</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6274">6274</a>.</cite>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Look up <a href="https://en.wiktionary.org/wiki/Special:Search/internet_protocol" class="extiw external" title="wiktionary:Special:Search/internet protocol">internet protocol</a> in Wiktionary, the free dictionary.</div></div>

</div>

<ul><li><cite id="CITEREFManfred_Lindner" class="citation web cs1">Manfred Lindner. <a rel="nofollow" class="external text" href="https://www.ict.tuwien.ac.at/lva/384.081/datacom/09-IP_Technology_v6-3_handout.pdf">"IP Technology"</a> (PDF). Retrieved 2018-02-11.</cite></li>

<li><cite id="CITEREFManfred_Lindner" class="citation web cs1">Manfred Lindner. <a rel="nofollow" class="external text" href="https://www.ict.tuwien.ac.at/lva/384.081/datacom/10-IP_Routing_v6-2_handout.pdf">"IP Routing"</a> (PDF). Retrieved 2018-02-11.</cite></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Internet_Protocol_version_693" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Internet_Protocol_version_693" style="font-size:114%;margin:0 4em"> <a href="IPv6" title="IPv6">version 6</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">General</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="IPv6_address" title="IPv6 address">IPv6 address</a></li>

<li><a href="IPv6_packet" title="IPv6 packet">IPv6 packet</a></li>

<li><a href="Mobile_IP#Changes_in_IPv6_for_Mobile_IPv6" title="Mobile IP">Mobile IPv6</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Deployment</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="IPv6_deployment" title="IPv6 deployment">IPv6 deployment</a>

<li><a href="World_IPv6_Day_and_World_IPv6_Launch_Day" title="World IPv6 Day and World IPv6 Launch Day">World IPv6 Day and World IPv6 Launch Day</a></li>

<li><a href="Comparison_of_IPv6_support_in_operating_systems" title="Comparison of IPv6 support in operating systems">Comparison of IPv6 support in operating systems</a></li>

<li><a href="Comparison_of_IPv6_support_in_common_applications" title="Comparison of IPv6 support in common applications">Comparison of IPv6 support in common applications</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">IPv4 to IPv6 topics</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="IPv4_address_exhaustion" title="IPv4 address exhaustion">IPv4 address exhaustion</a></li>

<li><a href="IPv6_transition_mechanism" title="IPv6 transition mechanism">IPv6 transition mechanism</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related protocols</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="DHCPv6" title="DHCPv6">DHCPv6</a></li>

<li><a href="Internet_Control_Message_Protocol_for_IPv6" class="mw-redirect" title="Internet Control Message Protocol for IPv6">ICMPv6</a>

<ul><li><a href="Neighbor_Discovery_Protocol" title="Neighbor Discovery Protocol">Neighbor Discovery Protocol</a></li>

<li><a href="Multicast_Listener_Discovery" title="Multicast Listener Discovery">Multicast Listener Discovery</a></li>

<li><a href="Secure_Neighbor_Discovery" title="Secure Neighbor Discovery">Secure Neighbor Discovery</a></li>

<li><a href="Multicast_router_discovery" title="Multicast router discovery">Multicast router discovery</a></li></ul></li>

<li><a href="Site_Multihoming_by_IPv6_Intermediation" title="Site Multihoming by IPv6 Intermediation">Site Multihoming by IPv6 Intermediation</a></li></ul>

</div></td></tr></tbody></table></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-label="Navbox672" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Authority control databases: National </th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4482590-0">Germany</a></li><li><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph165187&CON_LNG=ENG">Czech Republic</a></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-31" href="https://en.wikipedia.org/wiki/?title=Internet_Protocol&oldid=1303537935">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>